Skip to main content
Feedback

Attachment Quotas tab

The Attachment Quotas tab allows private runtime cloud owners to manage the attachment quotas for their cloud, which define limits and configure capabilities for the cloud attachments created within that cloud. These quotas set limits for aspects such as maximum concurrent executions, disk usage, and message rates. Cloud owners set default quotas for all attachments but can also override them for individual attachments.

The Attachment Quotas tab appears on the Cloud Management page, but is disabled when creating a new runtime cloud.

When you select a private runtime cloud from the Clouds list on the left, the following is displayed on the tab:

  • All runtime cloud clusters in the selected Cloud
  • All accounts that have at least one runtime set up in the Cloud
  • For each account, the runtime that the account has set up in the Cloud
  • Some properties and values for the selected runtime

When you select a runtime on the left side of the tab, some of its properties and their values appear on the right. If a runtime cloud cluster is offline, its name and the accounts’ names appear in light gray text and you cannot see its property values.

private runtime cloud owners can view, edit, and save these property values on the Attachment Quotas tab.

  • When a Cloud owner sets a property value, the value appears in black text. If the Cloud owner has not entered a property value, the default value is used. Default values appear in light gray text.
  • If you enter a long number in bytes, text appears to the right in parentheses. It rounds your value to the nearest KB, MB, GB or TB.
  • For properties whose format is a positive integer in bytes, instead you can enter a whole number followed by KB, MB, GB or TB, such as 30 GB or 30GB.
  • For properties whose format is a positive integer in bytes, you cannot save negative numbers or numbers containing a decimal point.
  • Invalid entries appear in red and cannot be saved.

When a Cloud owner sets and saves property values for a runtime cloud cluster, those values are inherited by the basic runtimes installed in the runtime cloud cluster by the various accounts. However, if the Cloud owner has already set a property value for a runtime, it will not be overwritten by the runtime cloud cluster’s property value. This allows Cloud owners to set properties at the runtime cloud cluster level and propagate those values to the runtime cloud cluster’s basic runtimes, but also override the runtime property values if needed.

The runtime cloud cluster’s properties that you see here are stored in the <molecule_install_dir>/conf/container.properties file. The runtime’s properties that you see here are stored in the <molecule_install_dir>/conf/limits/<account_cloud_attachment_id> file. Although you can use a text editor to edit these properties in these files, it is easier and it is recommended that you edit them on the Attachment Quotas tab instead. If you use this tab to save these properties for an account, the account’s <molecule_install_dir>/conf/limits/ directory is created automatically.

note

Accounts that have a runtime attached to the Cloud do not have access to the Attachment Quotas tab. They can view, but not change, this information in the Account Properties dialog.

Account Concurrent Execution Limit
  • Default value - Unlimited
  • Format - Positive integer

The total number of concurrent executions allowed. If this field does not contain a value, there is no limit. On a Cloud, you must also set the Cloud Partition Size property for this limit to take effect. The Cloud Partition Size property is set in the Properties panel's Advanced tab under Runtime Management.

Account Concurrent Execution Warning Offset
  • Default value - Unlimited
  • Format - Positive integer

This value is subtracted from the Account Concurrent Execution Limit to determine when the runtime will generate a warning that the account is close to exceeding its number of concurrent executions.

For example, if this property is set to 5 and the Account Concurrent Execution Limit is set to 20, the runtime generates a warning in the container log when the account exceeds 15 concurrent executions. If this field does not contain a value, no warning is generated.

Account Disk Usage
  • Default value - Unlimited
  • Format - Positive integer, in bytes

Used to set the size limit for an account that uses this private runtime cloud.

API Request Input Size
  • Default value - Unlimited
  • Format - Positive integer, in bytes

For Web Services Server listener processes, limits the input size of a web service request. If this limit is reached, the request is rejected.

For Flow Services Server listener processes, limits the request size and response size. If this limit is reached on the request, the request is rejected with a 400 error code. If the limit is reached on a response, the request is rejected with a 503 error code.

Default AS2 Workload

  • Default value - Inherited (General)

  • Format - Choose one of the following:

    • Inherited - The setting is herited from the runtime cluster.
    • General - The default process mode for all new processes.
    • Low_Latency_Debug - All AS2 listener proccesses use an execution worker.

Used to select the process execution mode for AS2 listener processes. After you change this property value, you must restart the runtime cloud cluster or runtime.

For more information, refer to Process Options dialog and execution workerss.

note

If you select Low_Latency_Debug, Trading Partner components that use AS2 listeners will also use that execution mode.

Default HTTP Workload

  • Default value - Inherited (General)

  • Format - Choose one of the following:

    • Inherited - The setting is inherited from the runtime cluster.
    • General - The default process mode for all new processes. General mode processes do not use an execution worker, but Low_Latency mode processes do use one.
    • Low_Latency - All Web Services Server processes use an execution worker and run in Low_Latency mode
    • Low_Latency_Debug - All Web Services Server processes use an execution worker. Processes configured in General mode run in Low_Latency_Debug mode.

Used to select the process execution mode for Web Services Server processes. The Default HTTP Workload applies only to processes set to run in General mode. After you change this property value, you must restart the runtime cloud cluster or runtime.

For more information, refer to Process Options dialog.

Enabled Download of Execution Artifacts and Execution worker Logs

  • Default value - True

  • Format - Choose one of the following:

    • Inherited (false) - The setting is inherited from the runtime cloud cluster and the feature is turned off.
    • False - The feature is not enabled and users cannot download execution worker logs or execution artifacts.
    • True - (default) The feature is enabled and users can download execution worker logs and execution artifacts.
note

This property is automatically turned on for public runtime clouds.

Enable Processed Document Archiving

  • Default value - Inherited (false)

  • Format - Choose one of the following:

    • Inherited (plus the value of the setting being inherited)
    • False
    • True

If true or Inherited (true), the owner of the selected attached runtime is allowed to enable Processed document archiving.

Execution Worker Elastic Scaling Threshold
  • Default value - 75%
  • Format - Positive integer

The percentage value of current executions relative to the Execution Worker Maximum Running Executions that will trigger elastic scaling of additional workers.

Execution worker Maximum Execution Time
  • Default value - 0:0:30:0
  • Format - hr:min:sec:ms

Maximum execution time for execution worker processes. After this amount of time passes, a 522 HTTP status code message is returned to the client saying that the time limit has been exceeded. The process execution is canceled. After you change this property value, you must restart the runtime cloud cluster or runtime.

Execution worker Maximum General Execution Time
  • Default value - 0:10:0:0
  • Format - hr:min:sec:ms

Maximum execution time for execution worker processes that use Low_Latency_Debug mode. After you change this property value, you must restart the runtime cloud cluster or runtime.

Execution worker Maximum Queued Executions
  • Default value - 10
  • Format - Positive integer

Maximum number of extra processes that can be queued in a single execution worker, when the maximum number of processes is running. After you change this property value, you must restart the runtime cloud cluster or runtime.

Execution worker Maximum Running Executions
  • Default value - 20
  • Format - Positive integer

Maximum number of extra executions that can run in a single execution worker, when the maximum number of processes is running. After you change this property value, you must restart the runtime cloud cluster or runtime.

runtime Output Overflow Size
  • Default value - Unlimited
  • Format - Positive integer, in bytes

For execution worker processes, limits the number of bytes per output datastore maintained in memory before overflowing to disk.

Execution worker Queued Execution Timeout
  • Default value - 0:0:10:0
  • Format - hr:min:sec:ms

Maximum time that a queued job can wait to be executed. After this amount of time, the job fails with a timeout exception. After you change this property value, you must restart the runtime cloud cluster or runtime.

Execution worker Warmup Enabled

  • Default value - Inherited (Fals)

  • Format - Choose one of the following:

    • Inherited — The setting is inherited from the runtime cloud cluster.
    • False or Inherited (False) — The feature is not enabled.
    • True or Inherited (True) — When an execution worker is within 30 minutes of shutting down, the Cloud will start (“warm up”) another execution worker to replace it. When the execution worker that is ready to shut down stops running there is already another execution worker up and running, ready to take on its load. Setting this property to True ensures that there is no gap in coverage between the time when one execution worker stops and the next execution worker is initialized and begins to run. It ensures that there is always at least one execution worker available on which processes can be executed.

You can use this feature if your account is provisioned with at least one execution worker. If your account is provisioned with more than one execution worker, and if there are multiple execution workers within 30 minutes of shutting down, then by default only one execution worker is replaced. However, if one of those execution workers has a load greater than “LOW”, then it is replaced even though there is another execution worker running. If you have set the Minimum Execution workers property, then the appropriate number of execution workers are replaced so that you do not go below the minimum.

execution workers Working Overflow Size
  • Default value - Unlimited
  • Format - Positive integer, in bytes

For execution worker processes, limits the number of bytes per working datastore maintained in memory before overflowing to disk.

Execution workers
  • Default value - 0
  • Format - Positive integer

Number of execution workers allocated. This change takes effect immediately, assuming that the Cloud owner has already enabled execution workers on this runtime cloud.

Flow Control Parallel Processing Type Override
  • Default value - None
  • Format - None, Threads, or Processes

Overrides the Parallel Process Type setting in Flow Control steps at a global runtime cloud or Attachment Quota level. This property can be set only by a private runtime cloud owner.

HTTP Request Rate
  • Default value - Unlimited
  • Format - Positive integer

Limits the number of Web Services Server requests per second. This limitation is per node in the runtime cloud and per Cloud or runtime attachment. If this value is exceeded, callers receive a 503 error. After you change this property value, you must restart the runtime cloud cluster or runtime.

note

If an HTTP Request Rate value is set, API Management uses this limit before the values specified in the API Contract for Rate Limit or Quota Limit.

Maximum Concurrent Executions per Listener
  • Default value - 10
  • Format - Positive integer

The maximum number of concurrent executions allowed per listener—that is, the maximum listener pool size.

Maximum Connector Tracking Documents
  • Default value - 10,000
  • Format - Positive integer, less than or equal to 10,000

The maximum number of connector tracking documents that will be generated for a single connector step in a process execution. Once this limit is reached, no more tracking documents are reported to the platform for that step in the execution.

Minimum Execution workers
  • Default value - 0
  • Format - Positive integer

The minimum number of execution workers that run continuously in the Cloud.

If this property is set to a number greater than zero, then a few minutes after the Cloud starts and stabilizes, this number of execution workers begin to run. Their starting is not dependent upon receiving incoming process execution requests.

This property works in conjunction with the Execution worker Warmup Enabled property. If you set Minimum Execution workers greater than 0, then execution worker Warmup behavior is enabled as well. As your minimum number of execution workers reach the end of their lifespan, they are replaced with new execution workers.

If the load on active execution workers drops, the runtime cloud reduces the number of execution workers to the value you set for this property.

note

Setting this property to a number greater than the number of execution workers provisioned in your account does not cause additional execution workers to run. If you want additional execution workers provisioned to your account, contact Boomi Support.

Queue Commit Batch Limit
  • Default value - 100
  • Format - Integer Limit how many document batches can be committed to the atom queue at once. Currently hard-coded in the service. Note this has no impact when running on a basic runtime. Value must be set between 1 and 200 (default 100).
Queue Force File Persistence
  • Default value - False
  • Format - Boolean If true, forces documents to be persisted on disk instead of memory. This is more stable handling for large documents, but may perform slower.
Queue Maximum Batch Size
  • Default value - Unlimited
  • Format - Integer Limits how many documents can be configured to be in a batch. Users may configure a lower value in their Atom Queue send operation, but cannot configure a higher value.
Queue Maximum Document Size
  • Default value - Unlimited
  • Format - Integer Limits how large a document can be when sent to the queue. Documents larger than the quota will be rejected as failed.
Queue Message Throttle Rate
  • Default value - 0
  • Format - Positive integer (miliseconds) Length in milliseconds of an intentional pause to be inserted between messages.
Queue Server Incoming Message Rate Limit
  • Default value - Unlimited
  • Format - Positive integer

The maximum number of requests the attachment is allowed to send to the Shared Queue Server per minute. The limit is only enforced if the Incoming Message Rate Limit is set in the underlying cloud Queue Shared Server. If a value is not set or is less than 1, the Shared Queue Server limit is used. The message is rejected if the limit is exceeded and should be retried from within the integration process. The limit is enforced per cloud node.

Test Mode Maximum Aggregate Document Size
  • Default value - 10 MB
  • Format - Integer, in byes

The maximum aggregate data size across the execution of a process in test mode. A negative value means there is no maximum.

note

This field is present only if the enhanced test mode feature is enabled in the account. Contact your Boomi sales representative if you want to enable this feature.

Test Mode Maximum Document Count
  • Default value - 100
  • Format - Integer

The maximum number of files (documents) per inbound connector step during execution of a process in test mode. A negative value means there is no maximum.

note

This field is present only if the enhanced test mode feature is enabled in the account. Contact your Boomi sales representative if you want to enable this feature.

Reload Displays the most recently saved property values for the selected runtime cloud cluster or runtime.

Save Saves changes made to the property values for the selected runtime cloud cluster or runtime. Changes to some properties take effect after you restart the runtime cloud cluster or runtime. You must click Save before selecting a different runtime cloud cluster or runtime, otherwise your changes will be lost.